-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix problematic ERS cases #8422
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm assuming all the logging is intentional. I don't have a problem with it, it should help with analysis when things go wrong.
LGTM overall.
How do you feel about squashing the commits together?
I forgot this while reviewing.. |
Signed-off-by: Jacques Grove <[email protected]>
just a GTID UUID/SID without an offset/interval. Signed-off-by: Jacques Grove <[email protected]>
automatically in some cases (e.g. ERS); however, we were not resetting this sentinel flag in at least two cases: 1) When we have re-parented successfully (setMasterLocked) and 2) When we have successfully promoted a replica (PromoteReplica) Signed-off-by: Jacques Grove <[email protected]>
will make it easier to debug from log output. Signed-off-by: Jacques Grove <[email protected]>
Signed-off-by: Jacques Grove <[email protected]>
Already approved as #8319 ; redone to clean up the commit list which was polluted with hundreds of merge commits.
Description
do_not_replicate
flag on disk in some cases #8333 where we do not clear thedo_not_replicate
sentinel flag that we create during ERS (and other steps) to ensure that replication reporter does not automatically restart replication after we have (intentionally) stopped it.Checklist